Uniqueness
| Characteristic Name: | Uniqueness |
| Dimension: | Consistency |
| Description: | The data is uniquely identifiable |
| Granularity: | Record |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of duplicate records reported per thousand records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Ensure that every entity(record) is unique by implementing a key in every relation | (1) Key constraint |
| Ensure that same entity is not recorded twice under different unique identifiers | (1) Same customer is entered under different customer ID |
| Ensure that unique key is not-null at any cost | (1) Employee ID which is the key of employee table is not null at any cost |
| In case of using bar codes standardise the bar code generation process to ensure that Bar codes are not reused | (1) UPC |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain uniqueness of data records |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| A school has 120 current students and 380 former students (i.e. 500 in total) however; the Student database shows 520 different student records. This could include Fred Smith and Freddy Smith as separate records, despite there only being one student at the school named Fred Smith. This indicates a uniqueness of 500/520 x 100 = 96.2% | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
| duplicate vendor records with the same name and different addresses make it difficult to ensure that payment is sent to the correct address. When purchases by one company are associated with duplicate master records, the credit limit for that company can unknowingly be exceeded. This can expose the business to unnecessary credit risks. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| on two maps of the same date. Since events have a duration, this idea can be extended to identify events that exhibit temporal overlap. | H. Veregin, “Data Quality Parameters” in P. A. Longley, M. F. Goodchild, D. J. Maguire, and D. W. Rhind (eds) Geographical Information Systems: Volume 1, Principles and Technical Issues. New York: John Wiley and Sons, 1999, pp. 177-89. |
| The patient’s identification details are correct and uniquely identify the patient. | P. J. Watson, “Improving Data Quality: A Guide for Developing Countries”, World Health Organization, 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| The entity is unique — there are no duplicate values. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| Asserting uniqueness of the entities within a data set implies that no entity exists more than once within the data set and that there is a key that can be used to uniquely access each entity. For example, in a master product table, each product must appear once and be assigned a unique identifier that represents that product across the client applications. | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
| Each real-world phenomenon is either represented by at most one identifiable data unit or by multiple but consistent identifiable units or by multiple identifiable units whose inconsistencies are resolved within an acceptable time frame. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
Statistical validity
| Characteristic Name: | Statistical validity |
| Dimension: | Validity |
| Description: | Computed data must be statistically valid |
| Granularity: | Information object |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to lack of statistical validity in data |
| The number of complaints received due to lack of statistical validity of data |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Establish the population of interest unambiguously with appropriate justification (maintain documentation) | (1) Both credit customers and cash customers are considered for a survey on customer satisfaction. |
| Establish an appropriate sampling method with appropriate justification | (1) Stratified sampling is used to investigate drug preference of the medical officers |
| Establish statistical validity of samples -avoid over coverage and under coverage (maintain documentation) | (1) Samples are taken from all income levels in a survey on vaccination |
| Maintain consistency of samples in case longitudinal analysis is performed. (Maintain documentation) | (1) Same population is used over the time to collect epidemic data for a longitudinal analysis |
| Ensure that valid statistical methods are used to enable valid inferences about data, valid comparisons of parameters and generalise the findings. | (1) Poisson distribution is used to make inferences since data generating events are occurred in a fixed interval of time and/or space |
| Ensure that the acceptable variations for estimated parameters are established with appropriate justifications | (1) 95% confidence interval is used in estimating the mean value |
| Ensure that appropriate imputation measures are taken to nullify the impact of problems relating to outliers, data collection and data collection procedures and the edit rules are defined and maintained. | (1) Incomplete responses are removed from the final data sample |
Validation Metric:
| How mature is the process to maintain statistical validity of data |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| if a column should contain at least one occurrence of all 50 states, but the column contains only 43 states, then the population is incomplete. | Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Coherence of data refers to the internal consistency of the data. Coherence can be evaluated by determining if there is coherence between different data items for the same point in time, coherence between the same data items for different points in time or coherence between organisations or internationally. Coherence is promoted through the use of standard data concepts, classifications and target populations. | HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality. |
| 1) Accuracy in the general statistical sense denotes the closeness of computations or estimates to the exact or true values.
2) Coherence of statistics is their adequacy to be reliably combined in different ways and for various uses. |
LYON, M. 2008. Assessing Data Quality , Monetary and Financial Statistics. Bank of England. http://www.bankofengland.co.uk/ statistics/Documents/ms/articles/art1mar08.pdf. |